Increasing proficiency status of developers

ABSTRACT

The present disclosure relates to a tool for increasing efficiency of development and upskilling of developers of software. The system may be configured to identify minimum skills for development of a software tool, identify elements of the software tool to be provided, establish a maximum timeline for completion of the elements of the software tool, based on the elements identified, and determine a proficiency status level appropriate to complete the development of the software tool based on both the identified skills and the elements.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, claims priority to and thebenefit of, U.S. Ser. No. 14/569,979 filed Dec. 15, 2014 and entitled“METHOD, SYSTEM, AND COMPUTER PROGRAM PRODUCT FOR EFFICIENT RESOURCEALLOCATION.” The '979 application is a continuation of, claims priorityto and the benefit of, U.S. Ser. No. 13/710,706 filed Dec. 11, 2012 andentitled “METHOD, SYSTEM, AND COMPUTER PROGRAM PRODUCT FOR EFFICIENTRESOURCE ALLOCATION,” which issued on Jan. 6, 2015 as U.S. Pat. No.8,930,882. All of which are incorporated herein in by reference in theirentirety for all purposes.

FIELD OF DISCLOSURE

The present disclosure generally relates to measuring resourceeffectiveness. More particularly, the disclosure relates to methods,systems, and computer readable medium for efficient resource allocation.

BACKGROUND

Corporate sector companies and/or institutions such as banks,manufacturing companies, software firms, and the like (hereinafterreferred to as “institutions”), use human resources for execution of aproject. These institutions may want differently skilled human resourcesfor the project. The institutions may hire human resources oncontractual basis from a third party supplier and/or hire directly forthe project. At instances where the institution hires the humanresources from the third party supplier, the institution may provideconsideration to the third party supplier in exchange for the humanresources. The consideration may be based on skills, proficiency andexperience of the human resources as claimed by the third partysupplier. In some instances, one or more individuals of the hired humanresources may not show efficiency levels, proficiency and/or skills whendeployed on the project. The institution may have to train the one ormore human resources to enable the one or more human resources to reachto a proficiency to work on the project. As a result, the project mayget delayed. Also, the training may include investment on the one ormore human resources in terms of time, resources and/or compensation.Consequently, the institution may suffer losses due to delay in project,and investment on the one or more resources.

SUMMARY OF THE DISCLOSURE

The present disclosure improves upon existing systems and methods byproviding a tool for associating the proper resources to a developmentproject. For instance, according to various exemplary embodiments, acomputer based system for efficient resource allocation may beconfigured to identify minimum skills for development of a softwaretool. The computer based system may be further configured to identifyelements of the software tool to be provided. The computer based systemmay be configured to establish a maximum timeline for completion of theelements of the software tool, based on the elements identified. Thecomputer based system may be further configured to determine aproficiency status level appropriate to complete the development of thesoftware tool based on the identified skills and the elements.

According to various embodiments, the proficiency status levelappropriate to complete the development of the software tool, such as aminimum proficiency status level, may comprise a developer having aproficiency status level that is at least equal to the proficiencystatus level, such as this minimum proficiency status level. Thecomputer based system for efficient resource allocation may beconfigured to perform a skills assessment of a developer of the softwaretool. Also, the computer based system for efficient resource allocationmay be configured to perform a proficiency status level assessment of adeveloper of the software tool. The skills described herein may compriseat least one of technical software architecture skills, business processknowledge, and software tool interface knowledge. Software toolinterface knowledge may comprise of the ability to identify anddifferentiate work objects, work folders, and work cover.

According to various exemplary embodiments, the proficiency status levelmay comprise at least one of a beginner, minimum, experienced, core, andexpert. For instance, the beginner proficiency status level indicates adeveloper is able to design, write code and test a simple PegaRULESProcess Commander (PRPC) use case with guidance, has no business processknowledge, and no software tool interface knowledge. The minimumproficiency status level indicates a developer is able to design, writecode and test a simple PegaRULES Process Commander (PRPC) use caseindependently, has a minimum business process knowledge, and minimumsoftware tool interface knowledge. The experienced proficiency statuslevel indicates a developer is able to design, write code and test amoderate PegaRULES Process Commander (PRPC)/SD (Smart Disputes) use casewith guidance, has experience with business processes, has experiencewith software tool interfaces and can guide business rules teams. Thecore proficiency status level indicates a developer is able to design,write code and test a moderate PegaRULES Process Commander (PRPC)/SD usecase independently and utilize guidance to design, write code and test acomplex PegaRULES Process Commander (PRPC)/SD use case. The coreproficiency status level indicates the developer has core levelexperience which may include guidance with business processes, has corelevel experience with software tool interfaces and can guide businessrules teams and process design. The expert proficiency status levelindicates a developer is able to design, write code and test a complexPegaRULES Process Commander (PRPC)/SD use case independently and hasexpert level experience with business processes, has expert levelexperience with software tool interfaces and can guide business rulesteams and process design.

According to various exemplary embodiments, the computer based systemfor efficient resource allocation may be configured to assign adeveloper having the appropriate proficiency status level to thedevelopment of the software tool.

The computer based system for efficient resource allocation may beconfigured to evaluate the projected timeline based on the proficiencystatus level of the developer assigned. In many cases, the compensationof a developer may be based, at least in part, on a proficiency statuslevel of the developer. The elements of the software tool comprise anumber of flows, a number of user interface screens, a number ofactivities, and a number of connectors.

According to various exemplary embodiments, the computer based systemfor efficient resource allocation may be configured to transmitdeveloper proficiency status level designations to a third partysupplier of the developers. The computer based system for efficientresource allocation may be configured to enable at least one ofupskilling of a developer, knowledge increases by the developer, andgreater efficiency.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present disclosure will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference numbers indicateidentical or functionally similar elements. Additionally, the left-mostdigit of a reference number identifies the drawing in which thereference number first appears.

FIG. 1 is an efficient resource allocation system, in accordance withvarious embodiments of the present disclosure;

FIG. 2 is an exemplary block diagram for measuring resourceeffectiveness, in accordance with various embodiments of the presentdisclosure;

FIG. 3 is an exemplary report of a developer, in accordance with variousembodiments of the present disclosure;

FIG. 4 is a process flow for efficient resource allocation of adeveloper with a project tool, in accordance with various embodiments ofthe present disclosure; and

FIG. 5 is a block diagram of an exemplary computer system forimplementing the present disclosure, in accordance with variousembodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to method, system, and an article ofmanufacture for efficient resource allocation to a development project.The detailed description of exemplary embodiments of the presentdisclosure herein makes reference to the accompanying drawings andfigures, which show the exemplary embodiments by way of illustrationonly. While these exemplary embodiments are described in sufficientdetail to enable those skilled in the art to practice the presentdisclosure, it should be understood that other embodiments may berealized and that logical and mechanical changes may be made withoutdeparting from the spirit and scope of the present disclosure. It willbe apparent to a person skilled in the pertinent art that thisdisclosure can also be employed in a variety of other applications.Thus, the detailed description herein is presented for purposes ofillustration only and not of limitation. For example, the steps recitedin any of the method or process descriptions may be executed in anyorder and are not limited to the order presented.

The present disclosure is described herein with reference to systemarchitecture, block diagrams and flowchart illustrations of methods, andcomputer program products according to various aspects of the presentdisclosure. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flow diagramillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions.

The present disclosure is now described in terms of an exemplary systemin which the present disclosure, in various embodiments, is implemented.This is for convenience only and is not intended to limit theapplication of the present disclosure. It will be apparent to oneskilled in the relevant art(s) how to implement the present disclosurein alternative embodiments.

FIG. 1 shows components of an exemplary efficient resource allocationsystem 100, in accordance with various embodiments of the presentdisclosure. Efficient resource allocation system 100 associatesappropriate resources to a development project. In one example, thedevelopment project may be a project for development of a software tool.The resource may be a human resource such as a developer or anyInformation technology (IT) professional (hereinafter referred to as“developer”). As shown in FIG. 1, efficient resource allocation system100 may include an identification module 102, a case type matrix 104,and a proficiency matrix 106 and an assessment module 108.

Identification module 102 may identify minimum skills for development ofthe software tool. The skills for development of the software tools mayinclude technical software architecture skills, business processknowledge, and/or software tool interface knowledge. Softwarearchitecture serves as the blueprint for both the system and theproject. The software architecture may include details related to codelanguage, code complexity, elements, relations between elements,properties of software etc., for the software tool to be developed. Adeveloper having software architecture skill may have good understandingand/or experience in designing and developing use cases associated withsoftware architectures.

Business process knowledge may be related to one or more businessprocesses in and/or associated with the developed software. Businessprocesses are a collection of tasks or structured activities related toeach other and to a business process, for development of the software.The business processes may be based on organizational structures,nomenclatures, project requirements, key resources, key contacts,financial specifications, and the like. A developer having businessprocess knowledge may have good understanding and/or experience indesigning and developing use cases for process flows, organizationalstructures, financial specifications, and the like, of the software.

Software tool interface knowledge may refer to knowledge associated withsoftware interface designing. Software interface knowledge may berelated to developmental knowledge about user interface (UI) screens,input-output modules, activities, connectors, and the like, of asoftware. A developer having software tool interface knowledge may havea good understanding and/or experience in designing and developing usecases for interfaces. The developer having software tool interfaceknowledge may identify and differentiate work objects, work folders, andwork cover.

Identification module 102 may store the identified minimum skills fordevelopment of a software tool. In one embodiment, identification module102 may store the identified minimum skills information in a memory (notshown) of efficient resource allocation system 100. In variousembodiments, identification module 102 may store the identified minimumskills in an external storage medium (not shown) associated withefficient resource allocation system 100. In various embodiments,identification module 102 may store the identified minimum skills in thememory and the external storage medium.

Case type matrix 104 identifies elements of the software tool. Theelements of the software tool may include a number of flows, a number ofuser interface screens, a number of activities, and a number ofconnectors, design of the software tool, alternative flows in thesoftware tool, and the like. In one embodiment, case type matrix 104 mayanalyze information, definition, and the like, associated with thesoftware tool to identify the elements of the software tool. In variousembodiments, case type matrix 104 may identify the elements based oninput from a software architect. Other techniques for identifyingelements of the software tool are contemplated herein. Case type matrix104 determines a maximum timeline for completion of development of thesoftware tool based on the elements identified. In one embodiment, casetype matrix 104 may analyze the elements to determine complexity, skillsto develop the elements, number of elements, complexity of each element,number of developers, time for developing each element, statisticaldata, software architect input, buffer time, and the like, to determinethe maximum time. In various embodiments, case type matrix 104 maydetermine the maximum time based on input of the software architect.

Proficiency matrix 106 may determine a proficiency status levelappropriate to complete development the software tool based on theidentified skills and the elements. Proficiency matrix 106 may analyzethe number of elements, the complexity involved in developing use casefor each element, duration for developing use cases for each element,skills for developing use cases for each element, the statistical data,and the like, to determine the proficiency status level needed todevelop the software tool. According to various exemplary embodiments,the proficiency status level may comprise at least one of a beginner,minimum, experienced, core, and expert levels. Alternatively, theproficiency status level may be defined on a coarser or on finer levelin comparison with the abovementioned proficiency status levels. Eachproficiency status level may indicate the capability of correspondingdeveloper for developing use cases appropriate to the proficiency statuslevel. The beginner proficiency status level indicates a developer isable to design, write code and test a simple PegaRULES Process Commander(PRPC) use case with guidance. The developer having the beginnerproficiency status level may not have business process knowledge, andsoftware tool interface knowledge. The PRPC may be a rules-drivenBusiness Process Management (BPM) system that includes enterprise rulesand process engine with tools for developing, deploying and evolvingbusiness process applications.

The minimum proficiency status level indicates a developer is able todesign, write code and test a simple PRPC use case independently. Thedeveloper having the minimum proficiency status level may have a minimumbusiness process knowledge, and minimum software tool interfaceknowledge. The experienced proficiency status level indicates adeveloper is able to design, write code and test a moderate PRPC/SD(Smart Disputes) use case with guidance. The developer having theexperienced proficiency status level may have experience with businessprocesses and software tool interfaces, and can guide and/or leadbusiness rules teams. The core proficiency status level indicates adeveloper is able to design, write code and test a moderate PRPC/SD usecase independently. The developer having core proficiency status levelis also able to design, write code and test a complex PRPC/SD use casewith guidance. The developer having the core proficiency status levelindicates that the developer has core level experience with businessprocesses and software tool interfaces, and can guide business rulesteams and process design. The expert proficiency status level indicatesa developer is able to design, write code and test a complex PRPC/SD usecase independently. The developer having the expert proficiency statuslevel indicates that the developer has expert level experience withbusiness processes and software tool interfaces, and can guide businessrules teams and process design. Although, the proficiency status levelis defined for the developers able to design, write code and testdifferent levels of PRPC/SD use cases, it can be appreciated that theproficiency status level can be defined for the developers who are ableto design, write code and test use cases on different levels of otherbusiness process management systems as well. A card member or merchantinquiry that could not be resolved at the point of contact may comprisea CASE.

Proficiency matrix 106 may determine a proficiency status levelappropriate to complete development of use cases for the elements basedon the identified skills and the elements. For example, though any levelmay be determined, proficiency matrix 106 may determine that, aproficiency status level of a developer to develop a PRPC use caseassociated with a simple user interface element, is “beginner” or a setminimum status level and above. In another example, proficiency matrix106 may determine that a proficiency status level of a developer todevelop a PRPC use case associated with a performance critical elementin the software tool is “expert”.

Assessment module 108 may perform skills assessment of a developer ofthe software tool. Assessment module 108 may also perform a proficiencystatus level assessment of the developer of the software tool.Assessment module 108 may provide definition of elements of differentcomplexity levels to the developer to design, write code and test PRPCuse cases for elements of the software tool. The complexity level may bebroadly classified into, for example, simple, moderate and complex.Alternatively, the complexity level may be classified into finer or oncoarser levels. Assessment module 108 may determine the skills andproficiency status level of the developer. In one embodiment, assessmentmodule 108 may determine the skills and proficiency status level of thedeveloper a based on analysis of quality, timeliness and results of theuse cases developed by the developer. In various embodiments, assessmentmodule 108 may determine the skills and proficiency status level of thedeveloper a based on input from an evaluator evaluating the quality,timeliness and results of the PRPC use cases developed by the developer.According to various embodiments, assessment module 108 may determinethe skills and proficiency status level of the developer a based a testor set of tests.

To illustrate with an example, assessment module 108 may provide adefinition of a moderate level user interface window for a developerJohn Doe to design, write code and test a PRPC use case for the userinterface window of the software tool. Assessment module 108 mayevaluate the quality of the PRPC use case for the user interface windowprovided by John Doe, time taken for developing the PRPC use case andresult of the PRPC use case. Assessment module 108 may determine thatthe John Doe has core business process knowledge and has proficiency ofa core developer when John Doe independently completes the use casewithin a defined threshold quality metric, a defined threshold of timefor the experienced developer and provides a result within a definedthreshold result parameter. The threshold quality metric, the definedthreshold of time, and the defined threshold result parameter may bedefined by, for example, a software architect of the institution.Assessment module 108 may further assess John Doe to determine whetherJohn Doe has technical software architecture skills. Assessment module108 may determine that John Doe has technical software architectureskills and has proficiency status level of expert, when John Doecompletes the use case for the element of complex type within definedthresholds of quality, timelines and result parameter. This assessmentmay be revisited and/or reevaluated at any time, such as periodically,quarterly, and or semi-annually.

Assessment module 108 may assign developer proficiency status leveldesignations to the developer based on the skill assessment andproficiency status level assessment. Assessment module 108 may assignthe developer having the evaluated proficiency status level to thedevelopment of the software tool at an appropriate proficiency statuslevel. Using the example above, John Doe may be assigned in developmentof complex PRPC use cases for the elements of the software tool.Similarly, assessment module 108 may assess and assign other developershaving the appropriate proficiency status levels to the development ofthe software tool at an appropriate proficiency status levels. Forexample, assessment module 108 may assign a developer having minimumproficiency status level to develop PRPC use cases for simple elementsof the software tool. In another example, assessment module 108 mayassign a developer having core proficiency status level to develop PRPCuse cases for complex elements of the software tool.

Assessment module 108 may evaluate a projected timeline based on theproficiency status level of the developers assigned to development ofthe software tool. Assessment module 108 may generate the projectedtimeline based on the number of the developers having differentproficiency status levels. For instance, by aggregating and/or compilingthe timelines of the different developers assigned, an aggregated and/orcompiled timeline may be established. Assessment module 108 maydetermine compensation for the developers based on their correspondingproficiency status levels. Assessment module 108 may define differentcompensation bands for different proficiency skills. The compensationbands may be competitive or in par with standard compensation providedin market. Assessment module 108 may fix compensation for a developerbased on the proficiency status level. Assessment module 108 maygenerate a report comprising skills, proficiency status level,assessment information, and compensation details. Assessment module 108may communicate the report to, for example, a project head, humanresource officers, and/or the developer. Assessment module 108 maycommunicate developer proficiency status level designations and thereport to a third party supplier, such as a third party supplier ofdevelopers.

Assessment module 108 may use the skills and the proficiency statuslevel information to impart training to increase knowledge and skills ofthe developers, while the developers continue to work on projectdeliverables. In various embodiments, up-skilling of the developer mayoccur beginning with the assigned proficiency status level of thedeveloper. The up-skilling of the developer may include, in an example,identifying training requirements for the developer based on theproficiency status level within an assigned time period. For example, ifthe developer is assigned a beginner proficiency status level, thedeveloper may be asked to participate in one or more trainingactivities, such that the developer's proficiency status level may beimproved. The training activities may include knowledge share sessions,framework reviews, architecture reviews, business process and projectrequirements review, GDM architecture review, and the like. Thedeveloper may also be assigned active tasks assignments such asdocumenting software use cases, data table design, design of agents andbatch processing, designing process flows, development of userinterfaces, building connectors, and the like. The developer'sperformance in the training activities may be monitored to assessquality and overall improvement of the developer. Further, if thedeveloper completes tasks independently or with minimal guidance, thedeveloper may be given more challenging activities and use cases. Also,new training activities may be formulated to meet the development model.

In various embodiments, the proficiency status level assigned to eachdeveloper may be transmitted to a third party supplier the developers.The third party supplier may be, in an example, a company or a firmhaving a contract with the institution implementing efficient resourceallocation system 100. The third party supplier may provide a resourcepool to the institution for various projects. Based on the proficiencystatus level assigned to each developer, the third party supplier maydetermine, in coordination with the institution, factors such as numberof developers to be provided, time period of contract, overallcompensation, and the like. Further, the third party supplier mayrecruit new developers having skills, identified and appropriate fordevelopment of the software tool. Such a step may insure that goodquality resources are provided to the institution by the third partysupplier.

In an exemplary implementation, the developer may be assessedperiodically for determination of the proficiency status of thedeveloper. The period may be, for example, every six months, such thatknowledge and skill sets of the developer are updated. Further, theinstitution and the third party may have discussions over the assessmentof the developer to clear expectations and drive expectations of theinstitution. Furthermore, training plans and schedules may be updatedwhere necessary.

Although, the disclosure discusses about efficient resource allocationsystem 100 determining proficiency status level of a developer, fordevelopment of a software tool, efficient resource allocation system 100may also be used for other any other projects such as projects relatedto finance, research, security, and the like. Further, efficientresource allocation system 100 as described herein may be managed by aninstitution (not shown) and/or a third-party supplier of the vendor (notshown) associated with the institution.

In various embodiments, efficient resource allocation system 100 may beimplemented as a set of computer related instructions. In variousembodiments, efficient resource allocation system 100 may be configuredto execute a set of computer related instructions. The computer readableinstructions of corresponding modules and tools may be loaded onto ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions that execute on the computer or other programmable dataprocessing apparatus create means for implementing the functionsspecified in the flowchart block or blocks. These computer programinstructions may also be stored in a computer-readable memory that candirect a computer or other programmable data processing apparatus tofunction in a particular manner, such that the instructions stored inthe computer-readable memory produce an article of manufacture includinginstruction means which implement the function specified in theflowchart block or blocks. The computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions which execute on the computer orother programmable apparatus provide steps for implementing thefunctions specified in the flowchart block or blocks.

The system may be described herein in terms of functional blockcomponents, optional selections and various processing steps. It shouldbe appreciated that such functional blocks may be realized by any numberof hardware and/or software components configured to perform thespecified functions. For example, efficient resource allocation system100 may employ various integrated circuit components, e.g., memoryelements, processing elements, logic elements, look-up tables, and/orthe like, which may carry out a variety of functions under the controlof one or more microprocessors or other control devices. Similarly, thesoftware elements of efficient resource allocation system 100 may beimplemented with any programming or scripting language such as C, C++,Java, COBOL, assembler, PERL, Visual Basic, SQL Stored Procedures,extensible markup language (XML), with the various algorithms beingimplemented with any combination of data structures, objects, processes,routines or other programming elements. Further, it should be noted thatsystem 100 may employ any number of conventional techniques for datatransmission, signaling, data processing, network control, and/or thelike. Still further, system 100 could be used to detect or preventsecurity issues with a client-side scripting language, such asJavaScript, VBScript or the like.

FIG. 2 illustrates an exemplary project for which assessment ofresources is performed by the efficient resource allocation system. Inan example, the project may relate to development of an attendancemarking tool for an institution. As depicted, a project code “AttendanceSystem” may be designated to the project and various parameters relatedto assessment of the resources may be accumulated. The variousparameters may include proficiency status levels, number of use casesassigned, types of use case assigned, and number of resources identifiedto have the different proficiency status levels. As described in theforegoing, the different proficiency levels may include expert, core,experienced, minimum, and beginner. FIG. 2 displays various fields inconnection with the project. The fields include proficiency status levelfield, number of use cases field, type of use cases field, and number ofresources identified field. The proficiency status level field indicatesthe proficiency status level for a number of PRPC use cases (illustratedin number of use case field). The type of use cases indicate complexityinvolved in the PRPC use cases. The number of resources identified forthe use cases may indicate the resources assessed and assigned and/oravailable for completing the attendance system project. Although thefigure illustrates the proficiency status level field, the number of usecases field, the type of use cases field, and the number of resourcesidentified field, one can appreciate that other fields may be included.

In an example depicted in FIG. 2, for assessing the resources for expertproficiency status level, the resources may be provided with definitionsof elements to developers to design, write and test the PRPC use caseto. The attendance system may be a moderate level software for anenterprise. The definitions for elements may include instructions tocomplete a PRPC use case elements of the attendance system in astipulated time period. The overall performance and time taken by eachresource to complete the use case may be assessed and accumulated. Theproficiency status levels may be assigned to the developers based on theassessment of the resources. As shown in FIG. 2, only one resource isfound to have successfully designed, written and tested the PRPC usecase independently for architectural elements of the attendance system,within the stipulated time period. Thus, the number of resources to beassigned with an expert proficiency status level is one, as depicted.

As illustrated in FIG. 2, two developers have successfully designed,written and tested moderate level PRPC use cases, independently. The twodevelopers may not have successfully designed, written and testedcomplex level PRPC use cases, independently. The two developers may beassessed to be having core proficiency status level. For determining theexperienced proficiency status level, the resources may be given fivedifferent moderate use cases to work upon. These may be assigned to becompleted sequentially or concurrently and/or a combination thereof. Theexperienced proficiency status level may be assigned to the resourcesthat complete the moderate use cases, under supervision, withinstipulated time periods adhering to the provided instructions. Asdepicted in FIG. 2, three resources are found to have an experiencedproficiency status level. Similarly, for three developers have assessedto be at experienced proficiency status level, four developers have beenassessed to be at minimum proficiency status level and one developer hasbeen assessed to be at beginner proficiency status level.

FIG. 3 is a user interface view illustrating report including skills andproficiency status levels of developers. The skills and proficiencystatus level of the developers may be assessed as described above. FIG.3 illustrates a report of the developers John Smith and Joanne John.

As depicted by an example in FIG. 3, proficiency status levels areassigned to two different developers, i.e. developer 1 and developer 2.The report may include different fields providing information associatedwith the developer. In the current example, the fields in the reportinclude name of the developers, assessment, skill, assigned proficiencystatus levels, and compensation range. In other examples, fields otherthan those described in the figure may also be displayed. The otherfields may include designation of the developers, details about thirdparty provider of these developers, details regarding previouslycompleted projects, and the like. These parameters may be optionallydisplayed in a drop-down list, for example, by clicking an “Options”tab.

As shown in FIG. 3, for developer 1 (name “John Smith”) the expertiselevel report is based on results of an assignment which the developer 1has undergone. The assignment, in an example, may be formulated forassessing one or more developers, based on the identified skills fordevelopment of a software tool, identified elements of the softwaretool, and maximum timeline for completion of the identified elements.The assignment may include definitions of elements for the developers todesign, write code and test PRPC use cases. The assignment may beevaluated (at any time) and results of overall performance of each ofthe developers may be recorded and summarized in the assessment field.

Referring back to FIG. 3, for developer 1, the assessment field displaystime taken to complete the test, complexity of PRPC use cases completedand results associated with the assessment of developer 1. The test mayreflect a simulated need and/or an actual need of the institution (e.g.live vs. practice). As depicted, for developer 1 the completion time ofthe test is 31 days. Further, the assessment field summarizes that thedeveloper 1 can design, code, and test moderate PRPC use casesindependently. The assessment field further summarizes that thedeveloper 1 is experienced in software architecture and businessprocesses and can guide business rules teams. Based on the assessment,the developer 1 is recognized to have business process knowledge, andsoftware tool interface knowledge skill. The skill field associated withthe developer 1 illustrates the developer 1's skill. Further, based onassessment, an experienced proficiency status level is assigned todeveloper 1. The efficiency level associated with the experienced statuslevel is given as “level 2”. Compensation, to be given to developer 1may be based on the proficiency status level assigned to developer 1,i.e. experienced. Hence, compensation to be given to developer 1 fallsunder range 3, as depicted in compensation field of FIG. 3. Range 3 maybe a standard compensation scale provided to developers havingexperienced proficiency status level.

Similarly, for developer 2 (name “Joanne John”) the assessment fielddisplays time taken for completion of the test as 08 days. Theassessment field further displays that developer 2 can design, code andtest simple PRPC use cases with guidance. Further, as depicted, theassessment field summarizes that developer 2 does not have anyexperience in software interfaces, software architecture and businessprocesses. The skill field illustrates ‘NA’ indicating that thedeveloper 2 is just a beginner. Based on the assessment field and skillfield, a beginner proficiency status level is assigned to developer 2(illustrated in proficiency status level field). The efficiency levelassociated with the beginner proficiency status level is given as “level0”. The compensation to be given to developer 2 may also be based on theproficiency status level assigned (here “beginner”). Hence, as depicted,the compensation to be given to developer 2 falls under range 1.

In an example, a user using efficient resource allocation system 100such as a software architect, a project leader, a manager, and the like,may wish to see more details about the developers than that depicted inthe expertise level report. In an example, more details may be displayedin the expertise level report by clicking on the “options” tab. Forexample, the expertise level report for a developer may displayadditional details such as current project assigned to the developer,current project status, last evaluation date of the developer, date ofrecruitment of the developer, recent tasks and/or training completed bythe developer and the like. The additional information about thedeveloper may help the user to make an accurate assessment of thedeveloper.

In an exemplary implementation, the user may have an option of editingthe one or more fields for the developer displayed in FIG. 3. Forexample, if a certain developer is not experienced in softwarearchitecture but the user feels that the developer can still be assigneda proficiency status level of experienced, the user may do so. In suchan example, if the developer's compensation as evaluated by efficientresource allocation system 100 falls under range 2, the user may changethe compensation range for the developer to range 3. The user may changethe one or more fields by clicking “options” tab.

As depicted, the user may save the expertise level report and thecompensation details of the developer using “save” tab. The “displaynext” tab may be clicked for displaying assessment details for next twodevelopers. Further, “close” tab may be used for closing the currentfile, after the file has been saved by the user.

FIG. 4 illustrates a flowchart of an example process 400 for measuringresource effectiveness, according to various embodiments of the presentdisclosure.

Process 400 may start at step S402, where identification module 102identifies minimum skills for development of the software tool. Invarious embodiments, the skills may include technical softwarearchitecture skills, business process knowledge, and software toolinterface knowledge. The technical software tool interface knowledgeincludes an ability to identify and differentiate work objects, workfolders, and work folders. In an example, the identified skills arestored in the memory of efficient resource allocation system 100.

At step S404, case type matrix 104 may identify elements of the softwaretool. In various embodiments, the elements of the software tool mayinclude flows, UI screens, activities, and connectors. In an example,the elements of the software tool may be identified by case type matrix104 of efficient resource allocation system 100. At step S406, case typematrix 104 may identify a maximum timeline for completion of theelements of the software tool based on the identified elements. At stepS408, proficiency matrix 106 determines a proficiency status levelappropriate to complete the development of the software tool based onthe identified skills and the elements. The proficiency status level maybe one of beginner, minimum, experienced, core and expert.

At step S408, assessment module 108 may perform a skills assessment anda proficiency status level assessment of the developer of the softwaretool. In step S410, assessment module 108 may evaluate the projectedtimeline based on the proficiency status level of the developer. Theproficiency status level may also be utilized for determiningcompensation of the developer as well as up-skilling of the developer.In various embodiments, the proficiency status level designations of thedeveloper are transmitted to a third party supplier of a developer.

The present disclosure (i.e., system 100, process 400, or any part(s) orfunction(s) thereof) may be implemented using hardware, software or acombination thereof, and may be implemented in one or more computersystems or other processing systems. However, the manipulationsperformed by the present disclosure were often referred to in terms,such as comparing or checking, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form a part of the presentdisclosure. Rather, the operations are machine operations. Usefulmachines for performing the operations in the present disclosure mayinclude general-purpose digital computers or similar devices.

In fact, in accordance with various embodiments of the presentdisclosure, the present disclosure is directed towards one or morecomputer systems capable of carrying out the functionality describedherein. An example of the computer systems includes a computer system500, which is shown in FIG. 5.

The computer system 500 includes at least one processor, such as aprocessor 502. Processor 502 is connected to a communicationinfrastructure 504, for example, a communications bus, a cross over bar,a network, and the like. Various software embodiments are described interms of this exemplary computer system 500. After reading thisdescription, it will become apparent to a person skilled in the relevantart(s) how to implement the present disclosure using other computersystems and/or architectures.

The computer system 500 includes a display interface 506 that forwardsgraphics, text, and other data from the communication infrastructure 504(or from a frame buffer which is not shown in FIG. 5) for display on adisplay unit 508.

The computer system 500 further includes a main memory 510, such asrandom access memory (RAM), and may also include a secondary memory 512.The secondary memory 512 may further include, for example, a hard diskdrive 514 and/or a removable storage drive 516, representing a floppydisk drive, a magnetic tape drive, an optical disk drive, etc. Theremovable storage drive 516 reads from and/or writes to a removablestorage unit 518 in a well-known manner. The removable storage unit 518may represent a floppy disk, magnetic tape or an optical disk, and maybe read by and written on by the removable storage drive 516. As will beappreciated, the removable storage unit 518 includes a computer usablestorage medium having stored therein, computer software and/or data. Thecomputer system 500 further includes non-transitory, tangible computerreadable storage medium comprising the instructions disclosed and/orcontemplated herein.

In accordance with various embodiments of the present disclosure, thesecondary memory 512 may include other similar devices for allowingcomputer programs or other instructions to be loaded into the computersystem 500. Such devices may include, for example, a removable storageunit 520, and an interface 522. Examples of such devices may include aprogram cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an erasable programmableread only memory (EPROM), or programmable read only memory (PROM)) andassociated socket, and other removable storage units 520 and interfaces522, which allow software and data to be transferred from the removablestorage unit 520 to the computer system 500.

The computer system 500 may further include a communication interface524. The communication interface 524 allows software and data to betransferred between the computer system 500 and external devices.Examples of the communication interface 524 include, but may not belimited to a modem, a network interface (such as an Ethernet card), acommunications port, a Personal Computer Memory Card InternationalAssociation (PCMCIA) slot and card, and the like. Software and datatransferred via the communication interface 524 are in the form of aplurality of signals, hereinafter referred to as signals 526, which maybe electronic, electromagnetic, optical or other signals capable ofbeing received by the communication interface 524. The signals 526 areprovided to the communication interface 524 via a communication path(e.g., channel) 528. The communication path 528 carries the signals 526and may be implemented using wire or cable, fiber optics, a telephoneline, a cellular link, a radio frequency (RF) link and othercommunication channels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to media such as theremovable storage drive 516, a hard disk installed in hard disk drive514, the signals 526, and the like. These computer program productsprovide software to the computer system 500. The present disclosure isdirected to such computer program products.

Computer programs (also referred to as computer control logic) arestored in the main memory 510 and/or the secondary memory 512. Computerprograms may also be received via the communication interface 504. Suchcomputer programs, when executed, enable the computer system 500 toperform the features of the present disclosure, as discussed herein. Inparticular, the computer programs, when executed, enable the processor502 to perform the features of the present disclosure. Accordingly, suchcomputer programs represent controllers of the computer system 500.

In accordance with various embodiments of the present disclosure, wherethe present disclosure is implemented using a software, the software maybe stored in a computer program product and loaded into the computersystem 500 using the removable storage drive 516, the hard disk drive514 or the communication interface 524. The control logic (software),when executed by the processor 502, causes the processor 502 to performthe functions of the present disclosure as described herein.

In various embodiments, the present disclosure is implemented primarilyin hardware using, for example, hardware components such as applicationspecific integrated circuits (ASIC). Implementation of the hardwarestate machine so as to perform the functions described herein will beapparent to persons skilled in the relevant art(s).

As those skilled in the art will appreciate, a web client includes anoperating system (e.g., Windows NT, 95/98/2000/CE/Mobile, OS2, UNIX,Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventionalsupport software and drivers typically associated with computers. A webclient may include any suitable personal computer, network computer,workstation, personal digital assistant, cellular phone, smart phone,minicomputer, mainframe or the like. A web client can be in a home orbusiness environment with access to a network. In an exemplaryembodiment, access is through a network or the Internet through acommercially available web-browser software package. A web client mayimplement security protocols such as Secure Sockets Layer (SSL) andTransport Layer Security (TLS). A web client may implement severalapplication layer protocols including http, https, ftp, and sftp.

In various embodiments, components, modules, and/or engines of system100 may be implemented as micro-applications or micro-apps. Micro-appsare typically deployed in the context of a mobile operating system,including for example, a Palm mobile operating system, a Windows mobileoperating system, an Android Operating System, Apple iOS, a Blackberryoperating system and the like. The micro-app may be configured toleverage the resources of the larger operating system and associatedhardware via a set of predetermined rules which govern the operations ofvarious operating systems and hardware resources. For example, where amicro-app desires to communicate with a device or network other than themobile device or mobile operating system, the micro-app may leverage thecommunication protocol of the operating system and associated devicehardware under the predetermined rules of the mobile operating system.Moreover, where the micro-app desires an input from a user, themicro-app may be configured to request a response from the operatingsystem which monitors various hardware components and then communicatesa detected input from the hardware to the micro-app.

As used herein, the term “network” includes any cloud, cloud computingsystem or electronic communications system or method which incorporateshardware and/or software components. Communication among the parties maybe accomplished through any suitable communication channels, such as,for example, a telephone network, an extranet, an intranet, Internet,point of interaction device (point of sale device, personal digitalassistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone,kiosk, etc.), online communications, satellite communications, off-linecommunications, wireless communications, transponder communications,local area network (LAN), wide area network (WAN), virtual privatenetwork (VPN), networked or linked devices, keyboard, mouse and/or anysuitable communication or data input modality. Moreover, although thesystem is frequently described herein as being implemented with TCP/IPcommunications protocols, the system may also be implemented using IPX,Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH),or any number of existing or future protocols. If the network is in thenature of a public network, such as the Internet, it may be advantageousto presume the network to be insecure and open to eavesdroppers.Specific information related to the protocols, standards, andapplication software utilized in connection with the Internet isgenerally known to those skilled in the art and, as such, need not bedetailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS ANDPROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999);DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IPCLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THEDEFINITIVE GUIDE (2002), the contents of which are hereby incorporatedby reference.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish networks, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may includelocation-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.For more information regarding cloud computing, see the NIST's (NationalInstitute of Standards and Technology) definition of cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety.

In various embodiments the present disclosure is implemented using acombination of both the hardware and the software. The variousembodiments of the present disclosure have been described above, itshould be understood that they have been presented by way of example,and not limitation. It will be apparent to persons skilled in therelevant art(s) that various changes in form and detail can be madetherein without departing from the spirit and scope of the presentdisclosure. Thus, the present disclosure should not be limited by any ofthe above described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

In addition, it should be understood that the figures illustrated in theattachments, which highlight the functionality and advantages of thepresent disclosure, are presented for example purposes only. Thearchitecture of the present disclosure is sufficiently flexible andconfigurable, such that it may be utilized (and navigated) in ways otherthan that shown in the accompanying figures.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser windows, webpages, websites, web forms, prompts, etc. Practitionerswill appreciate that the illustrated steps described herein may comprisein any number of configurations including the use of windows, webpages,web forms, popup windows, prompts and the like. It should be furtherappreciated that the multiple steps as illustrated and described may becombined into single webpages and/or windows but have been expanded forthe sake of simplicity. In other cases, steps illustrated and describedas single process steps may be separated into multiple webpages and/orwindows but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In Re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. §101.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” Moreover, where a phrase similar to ‘at least one of A, B, and C’or ‘at least one of A, B, or C’ is used in the claims or specification,it is intended that the phrase be interpreted to mean that A alone maybe present in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described exemplary embodiments that are known to those ofordinary skill in the art are expressly incorporated herein by referenceand are intended to be encompassed by the present claims. Moreover, itis not necessary for a device or method to address each and everyproblem sought to be solved by the present disclosure, for it to beencompassed by the present claims. Furthermore, no element, component,or method step in the present disclosure is intended to be dedicated tothe public regardless of whether the element, component, or method stepis explicitly recited in the claims. No claim element herein is to beconstrued under the provisions of 35 U.S.C. 112, sixth paragraph, unlessthe element is expressly recited using the phrase “means for.” As usedherein, the terms “comprises”, “comprising”, or any other variationthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, article, or apparatus that comprises a list of elementsdoes not include only those elements but may include other elements notexpressly listed or inherent to such process, method, article, orapparatus.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

Further, the purpose of the foregoing Abstract is to enable the U.S.Patent and Trademark Office and the public generally, and especially thescientists, engineers and practitioners in the art who are not familiarwith patent or legal terms or phraseology, to determine quickly from acursory inspection the nature and essence of the technical disclosure ofthe application. The Abstract is not intended to be limiting as to thescope of the present disclosure in any way.

What is claimed is:
 1. A method comprising: determining, by acomputer-based system and using a proficiency matrix and using anassessment module, proficiency status levels appropriate to complete thedevelopment of a software tool, wherein the proficiency status levelsare based on an analysis of a maximum timeline for completion of theelements of the software tool using a case type matrix, minimum skillsfor development of a software tool using an identification module andelements of the software tool using the case type matrix; assigning, bythe computer-based system, use cases to developers; and increasing, bythe computer-based system, the proficiency status level of thedevelopers, in response to completion of the use cases.
 2. The method ofclaim 1, wherein the proficiency status level appropriate to completethe development of the software tool comprises a developer proficiencystatus level that is at least equal to the proficiency status level. 3.The method of claim 1, further comprising performing, by thecomputer-based system, a skills assessment of a developer of thesoftware tool.
 4. The method of claim 1, further comprising performing,by the computer-based system, a proficiency status level assessment of adeveloper of the software tool.
 5. The method of claim 1, wherein theminimum skills comprise at least one of technical software architectureskills, business process knowledge, or software tool interfaceknowledge.
 6. The method of claim 1, wherein the minimum skills comprisesoftware tool interface knowledge, and wherein the software toolinterface knowledge comprises an ability to identify and differentiatework objects, work folders, and work cover.
 7. The method of claim 1,further comprising transmitting, by the computer-based system, theproficiency status levels to a third party supplier of developers,wherein the third party supplier determines a number of developers to beprovided based on the received proficiency status levels, and a timeperiod of the contract based on the maximum timeline for completion. 8.The method of claim 1, wherein the proficiency status level is beginnerwhich indicates a developer is able to design, write code and test asimple PegaRULES Process Commander (PRPC) use case with guidance, has nobusiness process knowledge, and no software tool interface knowledge. 9.The method of claim 1, wherein the proficiency status level is minimumwhich indicates a developer is able to design, write code and test asimple PegaRULES Process Commander (PRPC) use case independently, has aminimum business process knowledge, and minimum software tool interfaceknowledge.
 10. The method of claim 1, wherein the proficiency statuslevel is experienced which indicates a developer is able to design,write code and test a moderate PegaRULES Process Commander (PRPC) usecase with guidance, has experience with business processes, hasexperience with software tool interfaces and can guide business rulesteams.
 11. The method of claim 1, wherein the proficiency status levelis core which indicates a developer is able to design, write code andtest a moderate PegaRULES Process Commander (PRPC) use case withguidance, and design, write code and test a core PegaRULES ProcessCommander (PRPC) use case with guidance, has core level experience withbusiness processes, has core level experience with software toolinterfaces and can guide business rules teams and process design. 12.The method of claim 1, wherein the proficiency status level is expertwhich indicates a developer is able to design, write code and test acomplex PegaRULES Process Commander (PRPC) use case independently, hasexpert level experience with business processes, has expert levelexperience with software tool interfaces and can guide business rulesteams and process design.
 13. The method of claim 1, further comprisingdetermining, by the computer based system, a number of developers to beprovided based on the received proficiency status levels, and a timeperiod of the contract based on the maximum timeline for completion. 14.The method of claim 1, further comprising evaluating, by thecomputer-based system, a projected timeline based on the proficiencystatus level of the developer assigned.
 15. The method of claim 1,wherein the compensation of a developer is based on the proficiencystatus level of the developer.
 16. The method of claim 1, wherein theelements of the software tool comprise at least one of a number offlows, a number of user interface screens, a number of activities, or anumber of connectors.
 17. The method of claim 1, further comprisingestablishing, by the computer-based system, the maximum timeline forcompletion of the elements of the software tool, based on the elementsidentified.
 18. The method of claim 1, further comprising enabling, bythe computer-based system, upskilling by a developer.
 19. A systemcomprising: a processor, a tangible, non-transitory memory configured tocommunicate with the processor, the tangible, non-transitory memoryhaving instructions stored thereon that, in response to execution by theprocessor, cause the processor to perform operations comprising:determining, by the processor and using a proficiency matrix and usingan assessment module, proficiency status levels appropriate to completethe development of a software tool, wherein the proficiency statuslevels are based on an analysis of a maximum timeline for completion ofthe elements of the software tool using a case type matrix, minimumskills for development of a software tool using an identification moduleand elements of the software tool using the case type matrix; assigning,by the processor, use cases to developers; and increasing, by theprocessor, the proficiency status level of the developers, in responseto completion of the use cases.
 20. An article of manufacture includinga non-transitory, tangible computer readable storage medium havinginstructions stored thereon that, in response to execution by acomputer-based system, cause the computer-based system to performoperations comprising: determining, by the computer-based system andusing a proficiency matrix and using an assessment module, proficiencystatus levels appropriate to complete the development of a softwaretool, wherein the proficiency status levels are based on an analysis ofa maximum timeline for completion of the elements of the software toolusing a case type matrix, minimum skills for development of a softwaretool using an identification module and elements of the software toolusing the case type matrix; assigning, by the computer-based system, usecases to developers; and increasing, by the computer-based system, theproficiency status level of the developers, in response to completion ofthe use cases.